View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001892 | T99X171.00 SKB Eagle | SW | public | 2024-02-14 16:17 | 2024-09-03 15:12 |
| Reporter | (ALTech) Sangmin Choi | Assigned To | (ALTech) Sangmin Choi | Due Date | |
| Priority | normal | Severity | s4-minor | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Summary | 0001892: Enable "Data Packet Length Extension" option in "Supported LE Features". | ||||
| Description | SKB Jira : https://jira.skbroadband.com/browse/NEXTRCU-34 There is an issue that voice packet transmission rate is low than other devices. RCU engineer told me the "Data Packet Length Extension" is set as "Not Used", so this issue happens. You can see the attached picture that "Data Packet Length Extension" is "False" for Eagle and "Data Packet Length Extension" is "True" for Smart3 Intek device. Could you please enable the "Data Packet Length Extension" option in "Supported LE Features" ? | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
|
|
|
|
|
Hello, Jason, Could you please check this ticket? If you find something, please send me the test firmware based on 542 branch first. Please let me know the schedule for test firmware. Thank you. Sangmin Choi. |
|
|
Hi Sangmin, The DPLE feature was disabled in BT FW when we developed ATV9 The information was shared from Mr. Yoon. Based on KAON box experience. we used the same brand of BT chip as KAON. There is the similar discussion as below, https://btracker-cns.fii-foxconn.com/vaas/view.php?id=1447 (The DPLE feature will impact UEI RCU, and most of Eagle's (BFX-AT100) user used UEI RCU) so for workaround other RCU, we modified it in package/apps/Bluetooth Thanks, Jason |
|
|
Hello, Jason, PPCP parameters (Connection Interval Min, Connection Interval Max, Max Connection Latency, Supervision Timeout, Min CE Length, Max CE Length) To resolve the voice packet drop issue, we set the PPCP parameters as (9, 9, 133, 1000, 0, 8) before. The workaround code was removed in case of SA02 RCU And, the voice packet drop issue happens again. The RCU can send the PPCP parameters only Connection Interval Min, Connection Interval Max, Max Connection Latency, Supervision Timeout. So, I think the workaround code may fix as follows. As-is: when the RTK_DEVICES is connected if the device is KR01 set the PPCP parameters as (8, 8, 133, 1000, 0, 8) else set the PPCP parameters as (9, 9, 133, 1000, 0, 8) To-be: when the RTK_DEVICES is connected if the device is KR01 // smchoi : I don't know about this line set the PPCP parameters as (8, 8, 133, 1000, 0, 8) else set the PPCP parameters as (value from RCU, value from RCU, value from RCU, value from RCU, 0, 8) Could you please check it? Thank you. Sangmin Choi. |
|
|
Hi Sangmin, I can not understand your request "value from RCU,". The reason we added for this commit was that we found that the value from RCU has problem (will have audio drop), so we added the workaround for it (because we can not controlled RCU FW) so I can not understand why we need to use the value from RCU. Thanks, Jason |
|
|
Hello, Jason, For example, PPCP parameters from SA01 RCU is as following. Connection Interval Min: 9 (11.25 msec) Connection Interval Max: 9 (11.25 msec) Max Connection Latency: 133 (number events) Supervision Timeout: 1000 (10 sec) And, PPCP parameters you added as workaround is as following. Connection Interval Min: 9 (11.25 msec) Connection Interval Max: 9 (11.25 msec) Max Connection Latency: 133 (number events) Supervision Timeout: 1000 (10 sec) Min CE Length: 0 (0 msec) Max CE Length: 8 (5 msec) It looks the voice packet drop issue is related with Max CE Length. But, Connection Interval Min, Connection Interval Max, Max Connection Latency, Supervision Timeout values can be set by RCU. So, I want to use Connection Interval Min, Connection Interval Max, Max Connection Latency, Supervision Timeout values from RCU. If you have any question, please let me know. Thank you. Sangmin Choi. |
|
|
Hello, Jason, As we discussed yesterday, please add workaround code for SA02 RCU. As-is: when the RTK_DEVICES is connected if the device is KR01 set the PPCP parameters as (8, 8, 133, 1000, 0, 8) else set the PPCP parameters as (9, 9, 133, 1000, 0, 8) To-be: when the RTK_DEVICES is connected if the device is KR01 set the PPCP parameters as (8, 8, 133, 1000, 0, 8) else if the device is SA02 set the PPCP parameters as (9, 9, 266, 1000, 0, 8) else set the PPCP parameters as (9, 9, 133, 1000, 0, 8) It should be applied only BFX-AT100_5.4.2 branch. And, add "[BPM-28432]" to prefix of commit message. Finally, this solution should be fixed in the future. Using current solution, if RCU change some parameter of PPCP, we should change the whole firmware. Thank you. Sangmin Choi. |
|
|
Hi Sangmin, Done, 2024-02-22 10:01:46 | jason.tf.ling@fii-.. | f5346b69a | packages/apps/Bluetooth | [BPM-2843] Update PPCP parameters for BRM-SA02 Thanks, Jason |
|
|
Hello, Jason, Thank you. There is a typo in commit message, but it's ok now. I close this ticket. Thank you. Sangmin Choi. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-02-14 16:17 | (ALTech) Sangmin Choi | New Issue | |
| 2024-02-14 16:17 | (ALTech) Sangmin Choi | Status | new => assigned |
| 2024-02-14 16:17 | (ALTech) Sangmin Choi | Assigned To | => (SW) Jason Ling |
| 2024-02-14 16:17 | (ALTech) Sangmin Choi | File Added: bt_snoop_sa02_bfx-at200.png | |
| 2024-02-14 16:17 | (ALTech) Sangmin Choi | File Added: bt_snoop_sa02_bfx-at100.png | |
| 2024-02-14 16:17 | (ALTech) Sangmin Choi | File Added: btsnoop_hci_sa02_bfx-at100.log | |
| 2024-02-14 16:17 | (ALTech) Sangmin Choi | File Added: btsnoop_hci_sa02_bfx-at200.log | |
| 2024-02-14 16:20 | (ALTech) Sangmin Choi | Note Added: 0015113 | |
| 2024-02-14 16:20 | (ALTech) Sangmin Choi | Issue Monitored: (ALTech) Younkwang Jung | |
| 2024-02-14 16:20 | (ALTech) Sangmin Choi | Issue Monitored: (ALTech) JunGyu Kim | |
| 2024-02-14 16:20 | (ALTech) Sangmin Choi | Issue Monitored: (ALTech) Wooshin Kang | |
| 2024-02-15 10:23 |
|
Note Added: 0015120 | |
| 2024-02-15 10:23 |
|
Assigned To | (SW) Jason Ling => (ALTech) Sangmin Choi |
| 2024-02-15 10:23 |
|
Note Edited: 0015120 | |
| 2024-02-20 14:22 | (ALTech) Sangmin Choi | Note Added: 0015163 | |
| 2024-02-20 14:22 | (ALTech) Sangmin Choi | File Added: PPCP_parameters_SA02.png | |
| 2024-02-20 14:22 | (ALTech) Sangmin Choi | Assigned To | (ALTech) Sangmin Choi => (SW) Jason Ling |
| 2024-02-20 19:42 |
|
Note Added: 0015165 | |
| 2024-02-20 19:42 |
|
Assigned To | (SW) Jason Ling => (ALTech) Sangmin Choi |
| 2024-02-21 15:54 | (ALTech) Sangmin Choi | Note Added: 0015167 | |
| 2024-02-22 09:01 | (ALTech) Sangmin Choi | Note Added: 0015170 | |
| 2024-02-22 09:01 | (ALTech) Sangmin Choi | Note Edited: 0015170 | |
| 2024-02-22 09:01 | (ALTech) Sangmin Choi | Note Edited: 0015170 | |
| 2024-02-22 09:02 | (ALTech) Sangmin Choi | Assigned To | (ALTech) Sangmin Choi => (SW) Jason Ling |
| 2024-02-22 10:24 |
|
Issue Monitored: (SW) Jacky Chiang | |
| 2024-02-22 10:24 |
|
Status | assigned => resolved |
| 2024-02-22 10:24 |
|
Resolution | open => fixed |
| 2024-02-22 10:24 |
|
Note Added: 0015172 | |
| 2024-02-22 10:24 |
|
Assigned To | (SW) Jason Ling => (ALTech) Sangmin Choi |
| 2024-02-22 10:43 | (ALTech) Sangmin Choi | Note Added: 0015173 | |
| 2024-09-03 15:12 | (ALTech) Sangmin Choi | Status | resolved => closed |
